The /v2/monitor/:id/checks/:checkId response now returns a structured
diff object (text / json) plus a snapshot.json for JSON-mode monitors.
Type both fields in the JS and Python SDKs so callers can branch on
the artifact kind instead of inspecting `unknown`.

Additive only: no method signatures change. Existing consumers that
ignored `diff` continue to work; new consumers can read
page.diff.{text,json} and page.snapshot.json.

# Conflicts:
#	apps/js-sdk/firecrawl/src/v2/types.ts

- diff.ts: replace JSON.stringify object comparison with a recursive
  deep-equal walker. Prevents spurious "changed" verdicts when the LLM
  returns the same fields in a different order between runs.
- diff-orchestrator.ts: treat empty markdown strings as a valid scrape
  result (only null/undefined trigger the missing-input fallback). A
  monitor of a page that legitimately renders no text now reports "same"
  on subsequent runs instead of a perpetual "changed".
- gcs-monitoring.ts: validate the parsed artifact shape before reading
  `parsed.kind`. Corrupt JSON or unexpected payload types (arrays,
  primitives, null) now surface as "no diff" instead of throwing and
  breaking the entire check-detail response.

* feat(monitoring): JSON-mode diff path with snapshot and markdown sidecar

Detect when a monitor's scrapeOptions.formats requests JSON extraction
(either {type:"json"} or {type:"changeTracking", modes:["json"]}) and
compute the diff against the previous scrape's doc.json instead of the
markdown text. Persist the JSON field diff + a snapshot of current
values to GCS under a kind-discriminated artifact, alongside the
existing markdown diff path.

When a monitor asks for both ["json","git-diff"] modes, compute both
diffs and attach the markdown unified diff as a sidecar on the JSON
artifact so a page whose markdown changed but JSON didn't (or vice
versa) reports status:"changed". Previously this combination silently
returned "same".

Shared compute-and-persist logic extracted into diff-orchestrator.ts
so the runner and the async result recorder go through one path.
Existing markdown-only monitors are unaffected; historical artifacts
without a "kind" field read back as markdown.

Adds three E2E snip tests: JSON happy path, changeTracking-json
normalization, mixed-mode acceptance.

* feat(sdk): type MonitorCheckPage.diff and add snapshot field

The /v2/monitor/:id/checks/:checkId response now returns a structured
diff object (text / json) plus a snapshot.json for JSON-mode monitors.
Type both fields in the JS and Python SDKs so callers can branch on
the artifact kind instead of inspecting `unknown`.

Additive only: no method signatures change. Existing consumers that
ignored `diff` continue to work; new consumers can read
page.diff.{text,json} and page.snapshot.json.

* fix(monitoring): address PR review feedback on diff path

- diff.ts: replace JSON.stringify object comparison with a recursive
  deep-equal walker. Prevents spurious "changed" verdicts when the LLM
  returns the same fields in a different order between runs.
- diff-orchestrator.ts: treat empty markdown strings as a valid scrape
  result (only null/undefined trigger the missing-input fallback). A
  monitor of a page that legitimately renders no text now reports "same"
  on subsequent runs instead of a perpetual "changed".
- gcs-monitoring.ts: validate the parsed artifact shape before reading
  `parsed.kind`. Corrupt JSON or unexpected payload types (arrays,
  primitives, null) now surface as "no diff" instead of throwing and
  breaking the entire check-detail response.

* Nick: other sdks

---------

Co-authored-by: Nicolas <20311743+nickscamara@users.noreply.github.com>